Release 10.1A: OpenEdge Application Server:
Administration

Setting up Transaction Servers

To set up a Transaction Server to support part of an international WebSpeed application, set up the environment in which it runs and configure its agent pool to access the appropriate data. To simplify configuration and maintenance, consider creating a subdirectory for each language or nationality. Similarly, consider placing databases, parameter files, and other resources in directories specific to the language or nationality.

When setting up a Transaction Server’s environment, you must ensure that when a message is issued by a WebSpeed agent, the Transaction Server displays it in the appropriate language. To accomplish this, set the PROMSGS variable in the ubroker.properties file’s Environment section for each Transaction Server definition. You cannot set PROMSGS at a system level, because multiple Transaction Servers requiring different translations of messages will run simultaneously. The international PROMSGS files have a three-letter extension that indicates the language. The following example sets PROMSGS to the Japanese version of the messages file:

PROMSGS=/usr/wsrt/prolang/jpn/promsgs.jpn; export PROMSGS

Define and configure your Transaction Servers as you would for a standard WebSpeed installation.

If it is important that you have messages displaying in the user’s language at all levels of the application, you can use the CGI-compatible Messenger. The NSAPI-compatible Messenger can use only one PROMSGS file, which you configure in its startup script. For the CGI Messenger, you can create a script file (based on wspd_cgi.sh) for each language and specify the appropriate PROMSGS file to use.